MBDR 0.31 integration note
The three primary HPE driver families below are already staged in the supplied
MBDR 0.31 rescue image and will be matched by Windows during boot. You do not
need to run the manual loader before opening Password Recovery.
The fallback versions remain separate; they are not staged automatically.
The remainder of this file is the ORIGINAL standalone-pack guide and applies
when using this folder with an older rescue image.

MBDR - HPE ProLiant ML350 Gen10 RAID driver pack
Prepared 14 October 2026

PURPOSE
These storage drivers are for making the server's RAID volume visible in
MBDR Rescue. Once the volume is accessible, Password Recovery can search
it for Windows installations. The same storage access also helps Data Recovery.

This is an add-on driver pack, not a bootable ISO. It does not change the
password recovery program. The existing rescue ISO/USB has not been rebuilt.
Copying this folder to a USB does NOT automatically load the new drivers.

WHAT IS INCLUDED
Primary drivers:
  SR hardware RAID: 1016.38.0.1003
    E208i-a, E208i-p, E208e-p, P408i-a, P408i-p, P408e-p, P816i-a.
  S100i software RAID: 1010.14.0.0(C), Windows Server 2022 package.
  P824i-p MR hardware RAID: 6.714.18.0, Windows Server 2019 package.

Separate fallback drivers:
  SR: 1010.84.0.1012(B), Windows Server 2016 package.
  S100i: 106.12.6.0(D), Windows Server 2016/2019 package.

The package names describe HPE's supported server operating systems. These
are candidates for MBDR's x64 Windows PE build 26100. Their x64 files and INF
OS model sections were checked, but this is not a claim of HPE WinPE
certification or a successful test on your server.

USE WITH THE EXISTING RESCUE USB
1. Extract the ZIP. Copy the whole MBDR-HPE-ML350-Gen10-Drivers folder onto
   the rescue USB's writable partition, or onto a separate USB stick.
2. Boot MBDR Rescue on the ProLiant, then open its command prompt.
   Shift+F10 may open it if that shortcut is enabled in the rescue session.
3. Run LOAD-PRIMARY-DRIVERS.cmd from the copied folder. For example, if the
   folder is on D:, the command is:

   "D:\MBDR-HPE-ML350-Gen10-Drivers\LOAD-PRIMARY-DRIVERS.cmd"

   The USB letter may be different after booting. Use the actual letter.
4. Return to Password Recovery and search for Windows installations again.

The loader refuses to run in normal Windows. It loads the three primary
families into the current rescue session; Windows handles hardware matching.
It does not install into the server's offline Windows installation, edit
accounts, change RAID configuration, or update controller firmware.

IF THE DISK IS STILL MISSING
Save %TEMP%\MBDR-HPE-driver-load.log to the USB before restarting. Also save
X:\Windows\INF\setupapi.dev.log if available. Record the controller name
and firmware version from iLO or the server's storage information screen.
A loader success message alone does not prove disk or array visibility.

HPE recommends SR firmware 8.23 with the newest SR driver. No firmware is
included here. Driver/firmware pairing and the array's health still matter.
Do not initialize, format or recreate an existing array to make it visible.

Fallbacks are for controlled tests. Reboot before trying a different version
of the same driver, and do not run the primary loader on that fallback test.
Use drvload with the appropriate INF in the Fallbacks folder. A driver
already loaded by the original boot image may prevent a different version
from taking over; that case needs a rebuilt boot image and a fresh boot.

VERIFICATION AND CONTENTS
All five installer packages and their .compsig files were downloaded from
downloads.hpe.com and checked against HPE's published SHA-256 hashes.
The original packages are retained in Packages; they were extracted, not run.
Drivers and Fallbacks contain the unmodified INF, CAT and runtime payloads,
including the S100i co-installer and P824i-p companion nodev.inf.
SOURCES.json records exact versions, source pages, URLs and vendor hashes.
DRIVER-INVENTORY.json records the INF versions and PCI hardware IDs.
SIGNATURE-VERIFICATION.json records local Windows signature verification.
SHA256SUMS.tsv covers the delivered pack files.

Licence texts are retained in Licences. This is a local-use pack for your
HPE server; redistribution in a public MBDR release needs a separate review.
Actual disk visibility and Password Recovery operation on the ProLiant have
not yet been tested. Drivers provide storage access; they do not unlock
BitLocker-encrypted volumes without the required recovery key.
